…1847)

…nd build helpers before SDK type check

Engine integration tests and benches still imported iii_sdk::UpdateOp, which
moved to iii_helpers::stream. The Node CI type-check step now also builds
@iii-dev/helpers so its subpath type declarations resolve.

…e clean break)

Add 0.20.0 entries for the @iii-dev/helpers extraction, the cross-language
parity renames/removals, and the engine/protocol/internal/utils submodule moves,
and correct the 0.20.0 index summary to state that the release is breaking (only
the first errors/channel/trigger/runtime slice keeps deprecated root aliases).

… retention

Add the StreamChangeEventDetail, Stream*Result, and MergePath name alignment to
the 0.20.0 parity entry, and correct the removals list: only FieldPath was
removed; MergePath is retained as a named export across the three SDKs.

bump_manifests bumped the iii-helpers crate/package to the prerelease but
left the dependency requirements pointing at the stable version, so cargo
(^0.19.4 vs 0.19.4-alpha.1) and pip (==0.19.4) could not resolve. Bump the
iii-helpers workspace-dep pin (root Cargo.toml) and the python iii ==pin,
mirroring iii-observability.

…i-observability (#1874)

- iii.rs: use Error (IIIError alias dropped from module scope)
- engine: import UpdateOp/UpdateOpError/MergePath from iii_helpers::stream
- regenerate Cargo.lock

… SDK root (#1891)

…ak (#1892)

main bumped the workspace to 0.19.5-next.1 but the helpers packages (added on
this branch) were still on their pre-rebase versions. Align @iii-dev/helpers
(node) and iii-helpers (python) to 0.19.5-next.1 / 0.19.5.dev1 to match the
rest of the workspace and regenerate the uv locks. (The rust iii-helpers crate
was already bumped during conflict resolution.)

Co-authored-by: Guilherme de S. Vieira Beira <guilherme.vieira.beira@gmail.com>
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

generate-api-docs.mts wrote the api-reference *.mdx but not their
<source>.skill.md siblings, so every regeneration left them stale and
tripped iii-skill-check verify-rendered. After writing each page, invoke
the canonical iii-skill-render binary on just that file (scoped to the
generated pages, not the whole docs root, to avoid touching unrelated
out-of-scope pages). Output is byte-identical to the committed siblings.

If iii-skill-render is not on PATH the step warns and continues so local
generation still works without it.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>